Added new routing logic for events based on severity and reasons, including CrashLoopBackOff, OOMKilled, and probe failures, with targeted receivers like Slack and Opsgenie. Introduced log level configuration for better control over log verbosity. Adjustments ensure more granular control and actionable notifications for critical issues.

Reorganized regex patterns into distinct list entries for better readability and maintainability. This change ensures clearer separation of match conditions, adhering to a more structured configuration format.

Consolidated repetitive match conditions into a more concise format using regex and single-line patterns. This reduces redundancy and improves maintainability while preserving functionality for event routing.

Adjusted alert routing rules to separate "CrashLoopBackOff," "OOMKilled," "Liveness probe failed," and "Readiness probe failed" events. Ensured specific events are routed to Slack or Opsgenie, while others are dropped to reduce noise. This improves clarity and maintainability of notification rules.

Replaced dashes with consistent indentation for improved readability and YAML structure accuracy. This adjustment ensures proper rendering and interpretation of templated match conditions.

Updated the drop rules in the YAML structure to ensure proper formatting under the `match` section. This resolves issues with the incorrect indentation, aligning with the expected syntax for Kubernetes event exporter configurations.